Skip to content

Conversation

@odeimaiz
Copy link
Member

@odeimaiz odeimaiz commented Oct 2, 2024

What do these changes do?

  • Display error message provided by the backend
  • Show "No message" text if the flash message is empty

ErrorMessage

Related issue/s

follows #6444

How to test

Dev-ops checklist

@odeimaiz odeimaiz self-assigned this Oct 2, 2024
@odeimaiz odeimaiz added t:enhancement Improvement or request on an existing feature a:frontend issue affecting the front-end (area group) labels Oct 2, 2024
@odeimaiz odeimaiz added this to the MartinKippenberger milestone Oct 2, 2024
@odeimaiz odeimaiz changed the title 🎨 [Frontend] Handle 5xx errors better 🎨 [Frontend] Handle LongRunningTask errors better Oct 2, 2024
@odeimaiz odeimaiz marked this pull request as ready for review October 2, 2024 11:46
@odeimaiz odeimaiz enabled auto-merge (squash) October 2, 2024 11:53
Copy link
Contributor

@GitHK GitHK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member

@pcrespov pcrespov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the video attached to the PR, are you using the latest version of the stack, including #6444 ? In theory, after that commit, unhandled exceptions are transformed into 500 with json-response as

{
  "error": {
      "status": 500, 
      "message": "We apologize for the inconvenience. Our team has recorded the issue and is working to resolve it as quickly as possible. Thank you for your patience [OEC: 1234]"
   }
}

and on the web-server logs you should get a comprehensive log with details of the exception including the context

@odeimaiz
Copy link
Member Author

odeimaiz commented Oct 2, 2024

In the video attached to the PR, are you using the latest version of the stack, including #6444 ? In theory, after that commit, unhandled exceptions are transformed into 500 with json-response as

{
  "error": {
      "status": 500, 
      "message": "We apologize for the inconvenience. Our team has recorded the issue and is working to resolve it as quickly as possible. Thank you for your patience [OEC: 1234]"
   }
}

and on the web-server logs you should get a comprehensive log with details of the exception including the context

Nope, the commit wasn't in yet.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 2, 2024

@odeimaiz odeimaiz merged commit cd50cbe into ITISFoundation:master Oct 2, 2024
51 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a:frontend issue affecting the front-end (area group) t:enhancement Improvement or request on an existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants